home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
049a
/
mlrun11.zip
/
MAILRUN.DOC
< prev
next >
Wrap
Text File
|
1992-01-23
|
4KB
|
73 lines
MAILRUN -- v1.1
Time and Date Stamping Utility
Copyright (c) 1991-1992 by Brian Showalter
All Rights Reserved
------------------------------------------------------------------------------
MAILRUN is a time and date stamping utility that provides BBS sysops with a
quick and easy way to notify their users when the last mail run was made.
MAILRUN can be used to update any text file that is less than 32,767 bytes in
size. This limitation exists because MAILRUN reads the entire text file into
memory to gain more speed in operation.
MAILRUN can be used to update any number of text files. First the system time
and date are retrieved and the update message is composed, and then the
message is inserted into each of the specified text files. If a prior update
message exists in a text file, it is replaced with the new message.
Why MAILRUN? I've looked at several similar programs, and none of them had
the one thing I was looking for - the ability to update multiple text files. I
place the "last mail run" message in several text files which are named
according to PCBoard's security levels as follows:
Level 20 = D:\PCB\GEN\20.
Level 30 = D:\PCB\GEN\30.
Level 40 = D:\PCB\GEN\40.
etc.
Doing this lets me restrict the "last mail run" message to only those users
which have access to the echoed conferences. The programs I looked at had to
be run once for each file, which took a bit longer and made the BBS event
batch file larger. So, I decided to "roll my own" and the result is MAILRUN.
------------------------------------------------------------------------------
OPERATING MAILRUN
The first thing you need to do before running MAILRUN for the first time is
create a .RUN file, which tells MAILRUN what message is to be created or
updated, and which text files are to contain that message. The .RUN file
should usually have the same name as the network for which mail runs are made
(e.g. INTELEC.RUN = Intelec network, ILINK.RUN = ILink network, etc.) For
more details on what goes into the .RUN file, refer to the sample INTELEC.RUN
file included in this package.
MAILRUN.EXE can be placed into the same subdirectory as your event batch
file, or it can be placed in any subdirectory. The only stipulation is that
the .RUN files MUST be in the same subdirectory as MAILRUN.EXE. To add
MAILRUN to your event, insert the following line:
MAILRUN <filename>
where <filename> contains the name of the .RUN file. Do NOT include the
".RUN" extension in this name. MAILRUN will append this extension
automatically. The above line should be inserted in your event batch file at
exactly the point where you want the date and time to be recorded. I normally
place it right after the command which inserts echoed messages into the BBS.
------------------------------------------------------------------------------
MAILRUN is copyrighted by Brian Showalter. You may use it as much as you want
and the author does not expect any compensation for its use. If you feel that
you absolutely, positively have to compensate me, you can call my BBS at (703)
433-6903 and upload some good files. You may also copy MAILRUN and give it to
your friends, and you may upload it to any bulletin board system, as long as
no modifications have been made to the original files.
If you find any nasty bugs in MAILRUN or wish to suggest enhancements, you can
leave me a message on my BBS, or you can send a message to me in the Sysops
conference on the Intelec or ILink echo networks.